Networking in SF
Nobody lands here with a network, so you are not behind if you don’t have one. This page shows you where the events are listed, which rooms are worth paying for, and how to run all of it with a team still working India hours. Tell us what you’re short of below and we’ll point you at the two or three channels worth your evenings.
In any given week, this city runs more founder galas, hackathons, demo nights and late-night builder cafes than you could attend if attending were your job. Half the good ones are waitlisted before you hear about them. That density is what you moved for. It can also turn your calendar into a pile of events that produced nothing, which is the one thing your first 90 days should not produce.
Networking here splits into eight channels. Each has its own rules and its own way of failing. That is why one founder says six months of SF did more than nine years of New York, while another says the only thing worth attending was one small dinner. Both are right, because they picked different channels. You only need two or three of the eight, and the picker below helps you choose them.
Pick your channels
Pick channels by what you are short of, not by what sounds impressive. Impressive-sounding rooms are how people end up at mixers their business never needed.
Your picks here reset when you reload the page. The DM draft and the checklist further down are saved in your browser.
Finding the events
Most SF events never appear on Luma’s public discover page. By some counts, the large majority are unlisted. You only see them if you follow the host’s calendar. So don’t browse. Subscribe to ten or fifteen host calendars and let the events come to you.
Technical events run on a second rail: the Cerebral Valley calendar, which the AI crowd maintains and passes around as a shared sheet. Balu, who set up Sprinto’s US operations across two SF stints, never used Luma’s discover page at all. He ran his whole calendar off Cerebral Valley.
Partiful is the third layer. It carries house parties and socials rather than talks, and during SF Tech Week it fills with investor events because a16z sponsors it. It requires a US phone number, with no workaround, because login and invites arrive as texts from a US number. So sort your eSIM first. A working US number and a filled-out LinkedIn are basic networking equipment here.
The city’s permanent circuit of ticketed mega-mixers fails every part of that test, so skip it entirely. One or two high-value events a week beats five random ones. You are trying to run into the same people again and again, not to collect contacts. If an event asks for your LinkedIn or a short application, fill it out properly. The host is curating the room, and a blank profile gets rejected. Apply the day a listing posts, not the day before the event, because half the good ones waitlist.
The other half of the event world never gets listed at all. It lives in WhatsApp and Discord group chats, where hosts drop events early and intros get traded in real time. There is no application form. You get added by someone who has seen you twice, which is the same repeat-encounters logic at work. Once you have that context, ask outright. “Is there a group where this crew coordinates?” is a normal question here.
The annual anchor is SF Tech Week each October, run by a16z. The public calendar is maybe half of what happens that week. The value is in the unlisted side dinners, and you get into those by asking the hosts of the small events you did attend.
The cold DM
Cold DMs work here in a way they don’t in most cities, and length is what gives you away. Write yours now, while the rules are in front of you.
Saved in your browser. Nothing is sent anywhere.
This channel compounds with posting in public. Share a demo, a teardown or a real number, and the replies start flowing toward you instead.
Hackathons
Weekend builds run nearly every week, most of them AI-focused. Cerebral Valley and AI Tinkerers are the two calendars to watch. Building alongside people creates trust in a way small talk never does, so demo something even if it’s rough. A weekend of building leaves you with warmer contacts than a month of mixers would.
Coffee walks
The default first one-to-one here is not a conference room. It is a 30 to 45 minute walk with coffee, and you suggest it in those words: “want to do a coffee walk near the Mission?” Walking side by side makes candid conversation easier than sitting across a table.
If you are also running a company, treat three or four walks a week as the ceiling. Two or three is plenty, as long as each one ends with a concrete next step or an intro you owe.
Small dinners, and helping at events
An eight-person curated dinner produces more real relationships than a 200-person mixer. Hosting one is the strongest move a newcomer can make, and you don’t need to feel established to do it.
There is also a free step below hosting. Most SF events run understaffed, so message the organiser on the Luma page and offer to work check-in or take photos. That turns you from attendee into team, with a reason to talk to everyone who walks in. Thank the organisers on your way out either way. They are the best-connected and least-thanked people in the room, and helpers get invited back, sometimes onto the stage.
When you do host, borrow a trick from one serial host: go around the table and have each person introduce the person to their left instead of themselves. Everyone has a real conversation before dinner starts, and nobody gets to recite a pitch.
The recurring rooms
Relationships grow with frequency, so a weekly community builds trust much faster than a monthly one. If you are choosing between two groups, take the one that meets weekly. The desi founder communities, with how to get into each one, are mapped in the Desi Directory. Pick one anchor there. Then make sure at least half your meetings by month three happen outside it, for the reasons on the culture page.
A surprising share of this scene happens in workout clothes, with the pitch pressure removed. The weekends page has the rest of that circuit.
Then there are the rooms you pay to enter.
None of these rooms is necessary. They are shortcuts to density once the free channels are already working for you.
Your evenings are India’s mornings
This is where networking collides with your India team, and why people quietly stop showing up by month two. It is a schedule problem, not a stamina problem, and it has a one-time fix. The two rows below are the same day on both clocks.
Solve this once, structurally, instead of every night. Pick two protected event evenings a week and tell your India team they are fixed. Then move the recurring syncs to your early morning, which is their evening. Negotiating night by night is what fails, because it makes every event a decision, and eventually the answer is no.
Don’t pitch first
The strongest norm in this city is giving first, and people follow it more than a newcomer expects. Lead with curiosity or a useful offer, and let the other person ask what you’re building. Pitching in the first five minutes marks you as a taker. The full translation of this, including how to read the polite American no, is on the culture page.
The second rule is the follow-up. Send it within 24 hours, while they still remember you. Mention something specific from the conversation and include something useful, like a link or an intro offer. Never a generic “great to meet you.” And past the first dozen people, memory stops scaling. A plain spreadsheet of who you met, where, and what you owe them beats every networking app.
Networking as an operator
“What are you building?” still opens every conversation, so have an answer about your craft or the problem you own. “I work at X” ends conversations here in a way it doesn’t in Bangalore. Hiring moves through the dinner-and-group-chat network long before a job gets listed, and the person who pulls you into your next role will be someone who has watched you think out loud three times. If you’re technical, shipping something over a weekend is the fastest way to get noticed by the founders who are hiring.
Do this now
Tick these off as you go. Saved in your browser.
{{ progress }}